ci: the spawn-edge acceptance harness (tebako-runtime-ruby#211) - #126
Merged
Merged
Conversation
A minimal per-line gate for the driver spawn-plan bug class — ruby#121's argv[0] drop at plan apply, tebako#691's array-spawn of an exposed payload command failing days after the line shipped. No factory gate exercised "payload array-spawns a child through a spec-32 kind: executable edge"; the class surfaced only in a full metanorma compile. ci/spawn-edge presses two tiny fixture payloads (a consumer whose manifest carries the expose: edge, a provider exposing a command that echoes its argv), stages a scratch store with the runtime pair under test + the provider payload (the manifest mirror read back from the pressed image), and boots the consumer entry, which array-spawns the exposed command as system() and IO.popen legs and asserts the child received the exact argv. The scripts build nothing: the runtime arrives as the factory leg's artifacts, the press/readback tool is the leg's pin-verified tfs CLI. Verified locally on macos-arm64 against the published packages: ruby 4.0.7 and 3.3.12 of tebako 0.16.32 report SPAWN-EDGE-ACCEPTANCE-OK; the pre-fix 0.16.29 runtime fails the gate with the exact bug signature (the child's flag parse shifted, its provider mount lost, the entry resolving against the env image).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds a minimal spawn-edge acceptance harness under
ci/spawn-edge/— the fixture half of tamatebako/tebako-runtime-ruby#211. The runtime factory consumes it per ruby line × platform, after the boot smoke and before publish, so a driver spawn-plan regression (the argv[0]-drop class — #121, surfaced as tamatebako/tebako#691 and fixed in tebako v2.8.23) fails the leg instead of reaching a published runtime. No full metanorma compile involved: the whole gate is two tiny payloads and one boot.How it works
fixtures/— two payload trees:spawn-edge-provider1.0.0): exposes one command,spawn-edge-echo, which prints its receivedARGV.spawn-edge-probe): declares a criticalrequireson the provider's exposed command, then array-spawns it twice —system("spawn-edge-echo", "alpha", "beta gamma", "--flag=x", out: capture)andIO.popen([...])— asserting child exit 0 and the exact argv echo.run.sh(POSIX: linux-gnu, macos, and musl-in-alpine) andrun-msys.sh(windows; cygpath discipline,MSYS2_ARG_CONV_EXCL/MSYS2_ENV_CONV_EXCL='*', PE-named DLL staging) press both payloads withtfs mkimagein the default image format, stage a scratch store (runtime exe + env image + sha256 sidecars, provider payload + manifest mirror read back from the pressed image), and boot the leg's runtime exe against the consumer with the store onTEBAKO_HOME.SPAWN-EDGE-ACCEPTANCE-OK <ruby> (<triplet>)/FAIL spawn-edge (…); failures print the child's raw boot diagnostics, so the failing leg names the broken edge.Inputs:
RUNTIME_PKG_DIR(the leg's freshly built runtime package),RUBY_VERSION,TEBAKO_VERSION,TFS_CLI; optionalSCRATCH. Nothing is installed outside the scratch store; re-runs are idempotent.Evidence
Verified locally on macos-arm64 against published factory packages (tfs CLI 2.8.23, sha256-verified):
SPAWN-EDGE-ACCEPTANCE-OK, exit 0. (v0.16.32 passes because the factory's chain gate rolls this repo from main at build time — the argv[0] apply-side fix,b52aaf4, landed on main before that publish; the factory's pinned source release predates it.)--tebako-entry 'spawn-edge-echo': the env image declares no runtime entrypoint of that name — the parent's expose list outruns the runtime's spawn surface(the argv[0] drop shifts flag parsing and loses the provider mount). The harness catches the regression class it exists for.bundle exec rspec— 116 examples, 0 failures.bash -n,ruby -c, and YAML parsing all clean.Consumer
tamatebako/tebako-runtime-ruby#226 wires this into
_build-platform.yml, riding the pre-existingharness_refinput (defaultmain); until this lands on main, a probe dispatch withharness_ref: ci/spawn-edge-acceptanceexercises the gate end-to-end.